Issues

• CUT-4309 - Update Deploy-UserCertificate Functions to generate certs on SHA match

What does this solve?

This release aims to reduce the amount of time required to generate and deploy certificates for users. In previous iterations of this script, the tool would generate a new command each time the script was run for each user. This version changes the command "trigger" to the SHA1 hash of a user's certificate and compares that value when running Start-DeployUserCerts.

This release also introduces a multi-threaded operation when the tool generates commands for "new" or "all" users in the radiusMembers list.

Is there anything particularly tricky?

How should this be tested?

Functionality for the changes should be already covered in our Pester tests for this module. To validate the changes in this pull request. Pull the branch, open up the scripts/automation/Radius directory in a PowerShell session and run the pester tests on one of our Pester Tests orgs:

./tests/Invoke-Pester.ps1 -JumpCloudApiKey {YourPesterTestAPIKey}

In terms of updating from a previous version of the 2.0.0 development branch of radius certs:

• simply running this new version will generate new cert commands for each user, these new commands will have a trigger containing the SHA1 value of the user's cert. Subsequent times the script is run, commands for those users will not explicitly be re-generated unless the $forceGenerateCommands parameter is specified.

Before:

After:

Screenshots

Preliminary testing indicates that this version of the script runs about 47% faster than the previous version.

Newest version (running threads in parallel to generate commands)

Previous version (running single threaded and in sequence to generate commands)